Skip to content

⚡ Bolt: Parallelize bulk cache deletion using TaskGroup sliding window#252

Closed
acebytes wants to merge 1 commit into
mainfrom
bolt/optimize-cache-cleaner-taskgroup-9515336209934025715
Closed

⚡ Bolt: Parallelize bulk cache deletion using TaskGroup sliding window#252
acebytes wants to merge 1 commit into
mainfrom
bolt/optimize-cache-cleaner-taskgroup-9515336209934025715

Conversation

@acebytes
Copy link
Copy Markdown
Contributor

💡 What: Refactored removeContents to use withThrowingTaskGroup with a sliding window approach (maxConcurrency = 8) and made it a nonisolated async throws method with an injected FileManager.
🎯 Why: Previous implementation deleted directory contents sequentially on the actor's executor, causing slow, serialized disk I/O when cleaning caches with thousands of files. The TaskGroup securely parallelizes file deletion and retains original fail-fast semantics without legacy GCD or custom locks.
📊 Impact: Substantially speeds up cache deletion by parallelizing FileManager.removeItem calls safely within Swift's structured concurrency model.
🔬 Measurement: Observe faster cleanup times for large cache directories (e.g., Xcode DerivedData) in the application.


PR created automatically by Jules for task 9515336209934025715 started by @acebytes

Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@acebytes
Copy link
Copy Markdown
Contributor Author

Duplicate of #257 — same nonisolated removeContents + sliding-window TaskGroup pattern in CacheCleaner. #257 is the cleanest variant (no unnecessary inner Task.detached wrapping, which #257's own .jules note correctly identifies as pointless for cooperative-pool work).

@acebytes acebytes closed this May 17, 2026
@acebytes acebytes deleted the bolt/optimize-cache-cleaner-taskgroup-9515336209934025715 branch May 17, 2026 14:33
@google-labs-jules
Copy link
Copy Markdown
Contributor

Duplicate of #257 — same nonisolated removeContents + sliding-window TaskGroup pattern in CacheCleaner. #257 is the cleanest variant (no unnecessary inner Task.detached wrapping, which #257's own .jules note correctly identifies as pointless for cooperative-pool work).

Understood. Acknowledging that this work is a duplicate of #257 and stopping work on this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant